With this PR I propose to detail the expected user order for users with same contributions in Aggregation.kt.
To Highlight my point, I adapted the test respectively the expected user list:

• added Beth (with the same number of contributions as Bob) to the expected user list (1, 2).

The existing aggregate implementation failed with the adapted expected user list in my tests.
However, the test passes with the adapted expected user list with the proposed detailed user order.

Please note: the key selector of fun groupBy recognizes Bob first and Beth afterwards, because Bob is part of the second element of the actual user list. The existing tests would pass in case Beth would be recognized by the key selector prior to Bob (e.g. as part of the first user list element).

Additional change: gradle patch version bump.